┌ Error: Generated HTML over size_threshold limit: literated/splitting_supercell.md
│     Generated file size: 16.84 (MiB)
│     size_threshold_warn: 512.0 (KiB)
│     size_threshold:      1.0 (MiB)
│     HTML file:           literated/splitting_supercell/index.html
└ @ Documenter.HTMLWriter /usr/local/share/julia/packages/Documenter/xvqbW/src/html/HTMLWriter.jl:2000

We could increase the threshold, but this suggests the embedded images are large, maybe we can reduce the resolution? An alternative is to try again DisplayAs.PNG, but I know Greg wasn't a fan of that solution.

Oh, another alternative is to display the PNG images saved to disk, i.e. replace things like

save("supercell_warm_bubble.png", fig) #src
fig

with

save("supercell_warm_bubble.png", fig)
# ![](supercell_warm_bubble.png)

But again, the other PNG images we have seem to be a lot smaller.

Finally working: https://numericalearth.github.io/BreezeDocumentation/previews/PR398/literated/splitting_supercell/

https://numericalearth.github.io/BreezeDocumentation/previews/PR398/literated/splitting_supercell/

epic

Does anyone happen to know why one of the checks has been pending for hours?

It's not pending, it's a github UI glitch: it's a "required" check, but this PR only touches documentation and we don't run the tests jobs in that case to save resources, so they will never run anyway. The github UI shows the check as "pending" because they don't seem to have a concept of a job which is "required to pass when it runs, but could be skipped", for them "required" is always required to even run.

It's not pending, it's a github UI glitch: it's a "required" check, but this PR only touches documentation and we don't run the tests jobs in that case to save resources, so they will never run anyway. The github UI shows the check as "pending" because they don't seem to have a concept of a job which is "required to pass when it runs, but could be skipped", for them "required" is always required to even run.

Got it. In this case, how do we merge the PR? Use the command line?

If this is good to go (it is from my point of view, I don't know if @glwagner has more comments), we can bypass the required check

If this is good to go (it is from my point of view, I don't know if @glwagner has more comments), we can bypass the required check

Let’s wait to see if @glwagner has any additional comments.

unfortunately the preview has expired (and there are conflicts) --- once these are fixed, i would love to see the preview

unfortunately the preview has expired

When this happens, if you rerun the last "deploy-docs" (not the build one) job the preview should reappear in a couple of minutes.

@giordano I think this one is ready to be merged. I don’t see a bypass option on my end. Could you go ahead and merge it?